Add prerelease support to release workflow#61
Merged
Conversation
Coverage Report
File CoverageNo changed files found. |
When promoting from rc to stable, release notes now cover all changes since the last stable version, not just since the last rc. https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
…version types Instead of a separate prerelease input, add preminor, premajor, and prerelease directly to the newversion options. This maps directly to npm version commands and avoids confusion about input combinations. https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
… options Simpler UI: newversion stays as patch/minor/major, and a separate checkbox controls whether to release as rc. When checked and the current version is already an rc, it bumps the rc number instead. https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
Merge publish and release note steps by using DRY_RUN flag to conditionally add --dry-run or switch to preview mode, eliminating step duplication. https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
- PRERELEASE and DRY_RUN → workflow-level env - NEW_TAG, PREVIOUS_TAG, PREVIOUS_STABLE_TAG → publish job-level env - Remove redundant step-level env definitions https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
All input-derived env vars are now consistently defined at workflow level: NEW_VERSION_TYPE, PRERELEASE, DRY_RUN. https://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H
lollipop-onl
force-pushed
the
claude/add-prerelease-workflow-eNpEX
branch
from
e07b6ab to
2f9b2b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds support for creating prerelease versions in the release workflow. This allows publishing release candidates and other prerelease versions to npm with appropriate tags and GitHub release markers.
Changes include:
prereleaseinput parameter (choice between empty string for stable or 'rc' for release candidate)npm version prereleaseornpm version pre{major|minor|patch}--tagflag for prerelease versions--prereleaseflag for prerelease versionsTest plan
The release workflow can be tested by:
prereleaseset to empty string (stable release) - should behave as beforeprereleaseset to 'rc' - should create rc-tagged versions and publish with appropriate npm and GitHub release tagshttps://claude.ai/code/session_01ULoEJZPc1AfKpew9Pz8w9H